Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb3ced4b658bb98928ef2a9e5c4c734b12637bbc400e5cf2ceb16e4699810e05

Tx prefix hash: 51f391e7cb76abd0728df36538bd86461e68ef281f90201159e1f4627e3007ee
Tx public key: 7588b4c9dce52e88f714b975c9d28a7ca0149c1a2216cb30e30eb98d56a594ee
Timestamp: 1766095669 Timestamp [UCT]: 2025-12-18 22:07:49 Age [y:d:h:m:s]: 00:003:12:48:39
Block: 1436567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2534 RingCT/type: yes/0
Extra: 017588b4c9dce52e88f714b975c9d28a7ca0149c1a2216cb30e30eb98d56a594ee0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ab2c1063cb3f39b56a6178a439ff9e5358df5ef72a0b1a7a0565f3d66846b2f 0.600000000000 1925372 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": 1436577, "vin": [ { "gen": { "height": 1436567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ab2c1063cb3f39b56a6178a439ff9e5358df5ef72a0b1a7a0565f3d66846b2f" } } ], "extra": [ 1, 117, 136, 180, 201, 220, 229, 46, 136, 247, 20, 185, 117, 201, 210, 138, 124, 160, 20, 156, 26, 34, 22, 203, 48, 227, 14, 185, 141, 86, 165, 148, 238, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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