Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: aab3f8211a44e46a3aabe3db057fabed8c59f89a24ac49149d0d371d7b6805d1

Tx prefix hash: 292c8a6e2b4abd1624292d0a05219875f3e822a53fc3faa63e5cf6a097751eff
Tx public key: c06962f8c19941e2e4cd86756290f0e87ca28773e1cb8dbc56a3672806471615
Timestamp: 1728618468 Timestamp [UCT]: 2024-10-11 03:47:48 Age [y:d:h:m:s]: 00:208:16:15:38
Block: 1129003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148956 RingCT/type: yes/0
Extra: 01c06962f8c19941e2e4cd86756290f0e87ca28773e1cb8dbc56a367280647161502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5cc8da80cf7040c78e65352d8ad705948d8dc126e2cfcb63e8e950a65f00a77 0.600000000000 1611826 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1129013, "vin": [ { "gen": { "height": 1129003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5cc8da80cf7040c78e65352d8ad705948d8dc126e2cfcb63e8e950a65f00a77" } } ], "extra": [ 1, 192, 105, 98, 248, 193, 153, 65, 226, 228, 205, 134, 117, 98, 144, 240, 232, 124, 162, 135, 115, 225, 203, 141, 188, 86, 163, 103, 40, 6, 71, 22, 21, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8