Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fbc7265b61783049002bca78680de7990b66a9f2ae6f40e04f6ec20294c5cb3

Tx prefix hash: 3df3517864ac3b7613b1abc1e75898ea9355b4e8d5233074643ff1f9bf41ec94
Tx public key: 0ecf92eaf758a1e28da4d31fa3df1086f2e48d39863f1b3a52cf1b8d81c95c6d
Timestamp: 1733854618 Timestamp [UCT]: 2024-12-10 18:16:58 Age [y:d:h:m:s]: 00:115:18:41:48
Block: 1172323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82532 RingCT/type: yes/0
Extra: 010ecf92eaf758a1e28da4d31fa3df1086f2e48d39863f1b3a52cf1b8d81c95c6d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb3a5769d888b065cd82a98a75d013a2603c3b810cc8c98b206bf6d83dda37d 0.600000000000 1658200 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": 1172333, "vin": [ { "gen": { "height": 1172323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb3a5769d888b065cd82a98a75d013a2603c3b810cc8c98b206bf6d83dda37d" } } ], "extra": [ 1, 14, 207, 146, 234, 247, 88, 161, 226, 141, 164, 211, 31, 163, 223, 16, 134, 242, 228, 141, 57, 134, 63, 27, 58, 82, 207, 27, 141, 129, 201, 92, 109, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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