Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 254adc76328714e42738cc21b8e09952196e8aeae889e47dcb3cb093c64aa367

Tx prefix hash: a0028d8faecdfd04d736cfaa6cd72efc212c9bea24b9884f537832ba11c7d05e
Tx public key: 8bc64162d3f05dbfa9e31699c56da73046f380fdbc40a7f5794f39d70450d7db
Timestamp: 1737413245 Timestamp [UCT]: 2025-01-20 22:47:25 Age [y:d:h:m:s]: 00:148:13:50:40
Block: 1201725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105934 RingCT/type: yes/0
Extra: 018bc64162d3f05dbfa9e31699c56da73046f380fdbc40a7f5794f39d70450d7db0211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4df69c006d2c3123ac8bdfecb50a21086a45bd874ab5f484259c8d0d4b4d6fb2 0.600000000000 1688382 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": 1201735, "vin": [ { "gen": { "height": 1201725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4df69c006d2c3123ac8bdfecb50a21086a45bd874ab5f484259c8d0d4b4d6fb2" } } ], "extra": [ 1, 139, 198, 65, 98, 211, 240, 93, 191, 169, 227, 22, 153, 197, 109, 167, 48, 70, 243, 128, 253, 188, 64, 167, 245, 121, 79, 57, 215, 4, 80, 215, 219, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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