Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b319d77f2c9b4585743fb35aad1d76f28a684be101fa808f690c35f5322d13c8

Tx prefix hash: 9cacb13f19566d5efa86f0eedc46b8bf95ed48e28f611735003a4cdea9190ce0
Tx public key: b04ce5a59cda8479614a2c34cdab9ee5b3fbac04036f1e4a490dc4376b59286a
Timestamp: 1747277636 Timestamp [UCT]: 2025-05-15 02:53:56 Age [y:d:h:m:s]: 00:187:14:56:33
Block: 1283168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131804 RingCT/type: yes/0
Extra: 01b04ce5a59cda8479614a2c34cdab9ee5b3fbac04036f1e4a490dc4376b59286a0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdc73d6e3cf8374633a3fe282e57d56692e910c98183284e486d6f3f96af367f 0.600000000000 1770585 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": 1283178, "vin": [ { "gen": { "height": 1283168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdc73d6e3cf8374633a3fe282e57d56692e910c98183284e486d6f3f96af367f" } } ], "extra": [ 1, 176, 76, 229, 165, 156, 218, 132, 121, 97, 74, 44, 52, 205, 171, 158, 229, 179, 251, 172, 4, 3, 111, 30, 74, 73, 13, 196, 55, 107, 89, 40, 106, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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