Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 546c84ac2f7b035d384db84bf3651fdd1f7b059f16769f039286d39a74537b66

Tx prefix hash: acdae3f99d56a3a15e8a0c4b8668c94ed9074a3e75db68852bdd9247b3cfc6cd
Tx public key: b442b5a9d1496f13b8dc1f8af55c54fa80443b7a3fd8f7dcb13f13baf37b93c2
Timestamp: 1685101035 Timestamp [UCT]: 2023-05-26 11:37:15 Age [y:d:h:m:s]: 02:005:04:54:25
Block: 768480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525835 RingCT/type: yes/0
Extra: 01b442b5a9d1496f13b8dc1f8af55c54fa80443b7a3fd8f7dcb13f13baf37b93c2021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.744644416000 dcy

stealth address amount amount idx
00: 4db741e120cfe2713dfd40356fdfb775621bcf4e5e9d4d0eb57ba58ef1d46da8 1.744644416000 1217681 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": 768490, "vin": [ { "gen": { "height": 768480 } } ], "vout": [ { "amount": 1744644416, "target": { "key": "4db741e120cfe2713dfd40356fdfb775621bcf4e5e9d4d0eb57ba58ef1d46da8" } } ], "extra": [ 1, 180, 66, 181, 169, 209, 73, 111, 19, 184, 220, 31, 138, 245, 92, 84, 250, 128, 68, 59, 122, 63, 216, 247, 220, 177, 63, 19, 186, 243, 123, 147, 194, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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