Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd04fc78f8a3716e61bced75e704e8008192944a39df7fc3dc6491f90d4ccc1

Tx prefix hash: 88d284c5e8a150fcd16114d4750031939c8c706882f0b4c33d9495a6e13dc936
Tx public key: 84a1e7cb3b1709e58ca9a9ef571a190afdbf2739f530d828cda1312630800ea0
Timestamp: 1736048748 Timestamp [UCT]: 2025-01-05 03:45:48 Age [y:d:h:m:s]: 00:305:19:12:36
Block: 1190478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216044 RingCT/type: yes/0
Extra: 0184a1e7cb3b1709e58ca9a9ef571a190afdbf2739f530d828cda1312630800ea002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb746ea2dfb273cd3ebc403d18bb47f877ed9a547d1de0cc3c1921e8c715654e 0.600000000000 1676995 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": 1190488, "vin": [ { "gen": { "height": 1190478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb746ea2dfb273cd3ebc403d18bb47f877ed9a547d1de0cc3c1921e8c715654e" } } ], "extra": [ 1, 132, 161, 231, 203, 59, 23, 9, 229, 140, 169, 169, 239, 87, 26, 25, 10, 253, 191, 39, 57, 245, 48, 216, 40, 205, 161, 49, 38, 48, 128, 14, 160, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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