Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de1584ab671cd6e1002e439b324e01f0766fd9560fa08f6fc848fb1f58621850

Tx prefix hash: 08842a249695c4a30f8e655a5a62e805c55d5586f7cf5708c7b8b79a150c07a5
Tx public key: d33571daa34001c29c0d4371bf4f1501a7a5d6e8a1f59adedc010524df13338d
Timestamp: 1731387248 Timestamp [UCT]: 2024-11-12 04:54:08 Age [y:d:h:m:s]: 00:147:20:04:32
Block: 1151866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105489 RingCT/type: yes/0
Extra: 01d33571daa34001c29c0d4371bf4f1501a7a5d6e8a1f59adedc010524df13338d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a41b401e00179873cc7527045c690cfa60320a66a5948cb5f07a7d3f910ed3c5 0.600000000000 1637449 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": 1151876, "vin": [ { "gen": { "height": 1151866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a41b401e00179873cc7527045c690cfa60320a66a5948cb5f07a7d3f910ed3c5" } } ], "extra": [ 1, 211, 53, 113, 218, 163, 64, 1, 194, 156, 13, 67, 113, 191, 79, 21, 1, 167, 165, 214, 232, 161, 245, 154, 222, 220, 1, 5, 36, 223, 19, 51, 141, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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