Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f48326b45b88bfa91bddcf7c2b27293c717f943d98ea063a6d67dca0170268

Tx prefix hash: 447e68c59b838feb96785b56e4897c98a5f4b8597011f6d9b24571985eb0a6bc
Tx public key: 59327570c6a9d2069739c0289f41678ee830d26d55c054c00a3a92c0ecad01ff
Timestamp: 1577114743 Timestamp [UCT]: 2019-12-23 15:25:43 Age [y:d:h:m:s]: 05:113:08:55:45
Block: 30017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230910 RingCT/type: yes/0
Extra: 0159327570c6a9d2069739c0289f41678ee830d26d55c054c00a3a92c0ecad01ff02110000000f8a2ee0d9000000000000000000

1 output(s) for total of 488.137396632000 dcy

stealth address amount amount idx
00: bb821703d73f18f379eab204a0b4c98cb7c5ab7d595848858b7d38f1c6cae323 488.137396632000 49545 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": 30027, "vin": [ { "gen": { "height": 30017 } } ], "vout": [ { "amount": 488137396632, "target": { "key": "bb821703d73f18f379eab204a0b4c98cb7c5ab7d595848858b7d38f1c6cae323" } } ], "extra": [ 1, 89, 50, 117, 112, 198, 169, 210, 6, 151, 57, 192, 40, 159, 65, 103, 142, 232, 48, 210, 109, 85, 192, 84, 192, 10, 58, 146, 192, 236, 173, 1, 255, 2, 17, 0, 0, 0, 15, 138, 46, 224, 217, 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