Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54eab601a118ad9f725654d3440d1cdc823ca7051f41ec9a9899a401fea40a6f

Tx prefix hash: 96fe2a7a7ab922ff6487d79cffd4ae24d76aa47ac4718a195adc5ac5bb3a4446
Tx public key: b172d180ce2480b5bdcd8a16aaee04890dd6d3b5e501368347ed1e556b86260d
Timestamp: 1663971717 Timestamp [UCT]: 2022-09-23 22:21:57 Age [y:d:h:m:s]: 02:198:15:21:12
Block: 594381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 663356 RingCT/type: yes/0
Extra: 01b172d180ce2480b5bdcd8a16aaee04890dd6d3b5e501368347ed1e556b86260d021100000001faf35c9c000000000000000000

1 output(s) for total of 6.585201611000 dcy

stealth address amount amount idx
00: 481e3d4c01d3bb6351f888a1aa5bf49fbeb5bf336a80c0dcd18fe41cd123a5aa 6.585201611000 1029266 of 0

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": 594391, "vin": [ { "gen": { "height": 594381 } } ], "vout": [ { "amount": 6585201611, "target": { "key": "481e3d4c01d3bb6351f888a1aa5bf49fbeb5bf336a80c0dcd18fe41cd123a5aa" } } ], "extra": [ 1, 177, 114, 209, 128, 206, 36, 128, 181, 189, 205, 138, 22, 170, 238, 4, 137, 13, 214, 211, 181, 229, 1, 54, 131, 71, 237, 30, 85, 107, 134, 38, 13, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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