Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 329ad06fae8533eed7ccbfbc76dd7cacb2fedf96266cbb602d9bb07e537d0345

Tx prefix hash: 9eb7fcf1113d5f90d3420bb17fdd27b666910863537783c91afb3a6e66d38b47
Tx public key: 0a648fdc3cfe4c40f64e07a6befac41349975a17e195611cfe8a604a6990db4f
Timestamp: 1722829766 Timestamp [UCT]: 2024-08-05 03:49:26 Age [y:d:h:m:s]: 00:171:10:47:57
Block: 1081012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122623 RingCT/type: yes/0
Extra: 010a648fdc3cfe4c40f64e07a6befac41349975a17e195611cfe8a604a6990db4f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49ad2cb62d4b567b896c01d33cd6f8d0a658c90c6a2d44cecb2fd82f4529730f 0.600000000000 1554593 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": 1081022, "vin": [ { "gen": { "height": 1081012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49ad2cb62d4b567b896c01d33cd6f8d0a658c90c6a2d44cecb2fd82f4529730f" } } ], "extra": [ 1, 10, 100, 143, 220, 60, 254, 76, 64, 246, 78, 7, 166, 190, 250, 196, 19, 73, 151, 90, 23, 225, 149, 97, 28, 254, 138, 96, 74, 105, 144, 219, 79, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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