Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7d058db646b546c26bfdd81595754bf167df79b31f722629733e18e53a0bb46

Tx prefix hash: 4e124839ddcf73f7fd4f0d3a65d1efe26c6d2ecaec6f3068fb75967c6bd6f443
Tx public key: 3c8d38a33fe7a26856e663b8d87ff554a175b1a2ca558a2dec36cc2655f62ecd
Timestamp: 1677946136 Timestamp [UCT]: 2023-03-04 16:08:56 Age [y:d:h:m:s]: 01:359:14:51:56
Block: 709795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517683 RingCT/type: yes/0
Extra: 013c8d38a33fe7a26856e663b8d87ff554a175b1a2ca558a2dec36cc2655f62ecd0211000000015029cbac000000000000000000

1 output(s) for total of 2.729948247000 dcy

stealth address amount amount idx
00: a44d01f37ad5dfc7333cfc1a792b4e4bd81012d1316cd292aab59c219a0ed842 2.729948247000 1153810 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": 709805, "vin": [ { "gen": { "height": 709795 } } ], "vout": [ { "amount": 2729948247, "target": { "key": "a44d01f37ad5dfc7333cfc1a792b4e4bd81012d1316cd292aab59c219a0ed842" } } ], "extra": [ 1, 60, 141, 56, 163, 63, 231, 162, 104, 86, 230, 99, 184, 216, 127, 245, 84, 161, 117, 177, 162, 202, 85, 138, 45, 236, 54, 204, 38, 85, 246, 46, 205, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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