Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3a16f948e3443fc1d00769a686fcb1540d7e2891d4aeecdc182b82e04f5934

Tx prefix hash: acd4f1b2df2adf7cb40f8ddfa5cb75fb01753754d38497b23cdce667c87276b1
Tx public key: bf050407f3cc2d5e196288c8b1c422f1e120ac17286e980e2416bb9bb1894713
Timestamp: 1754896348 Timestamp [UCT]: 2025-08-11 07:12:28 Age [y:d:h:m:s]: 00:006:11:38:39
Block: 1344663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4015 RingCT/type: yes/0
Extra: 01bf050407f3cc2d5e196288c8b1c422f1e120ac17286e980e2416bb9bb1894713021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c6a48848677a1e12254e3d95258f0f790112c7f74dbeb237c6d6971f23430b1 0.600000000000 1832548 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": 1344673, "vin": [ { "gen": { "height": 1344663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c6a48848677a1e12254e3d95258f0f790112c7f74dbeb237c6d6971f23430b1" } } ], "extra": [ 1, 191, 5, 4, 7, 243, 204, 45, 94, 25, 98, 136, 200, 177, 196, 34, 241, 225, 32, 172, 23, 40, 110, 152, 14, 36, 22, 187, 155, 177, 137, 71, 19, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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