Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71048bd1ac3fd03d37d4909269da68e254ac75f0a498b4a4052a0525259411c7

Tx prefix hash: ea560064f94e68cad841f65d56eab7da85c8d20c300060bab1de50cd41bd9842
Tx public key: 3c6ec6ec16e81e97f3bfa90a0b1f044257aa24c5b650be2f30389df1363c699f
Timestamp: 1714295636 Timestamp [UCT]: 2024-04-28 09:13:56 Age [y:d:h:m:s]: 00:271:02:01:29
Block: 1010258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193984 RingCT/type: yes/0
Extra: 013c6ec6ec16e81e97f3bfa90a0b1f044257aa24c5b650be2f30389df1363c699f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 668c28dae5bef8e4b1922e4b1eb77da494df9c75b3e03560d5463a91c60ceca0 0.600000000000 1472160 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": 1010268, "vin": [ { "gen": { "height": 1010258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "668c28dae5bef8e4b1922e4b1eb77da494df9c75b3e03560d5463a91c60ceca0" } } ], "extra": [ 1, 60, 110, 198, 236, 22, 232, 30, 151, 243, 191, 169, 10, 11, 31, 4, 66, 87, 170, 36, 197, 182, 80, 190, 47, 48, 56, 157, 241, 54, 60, 105, 159, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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