Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78618af41372151edd07c62ba5897ee2e0b0c1e99bc34096b20f90a5647a111c

Tx prefix hash: d5fdb4d01f98f0ff6d06cd437e2386ce3e929fc35e712cb3ebda9d4ea28daf8f
Tx public key: 1e5d5130c6e254188afd07a3f1647b3e05024a0b11f5d0ea32f32d0be3914d95
Timestamp: 1687474274 Timestamp [UCT]: 2023-06-22 22:51:14 Age [y:d:h:m:s]: 01:126:09:33:12
Block: 788146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351719 RingCT/type: yes/0
Extra: 011e5d5130c6e254188afd07a3f1647b3e05024a0b11f5d0ea32f32d0be3914d9502110000000275e3f0e9000000000000000000

1 output(s) for total of 1.501568933000 dcy

stealth address amount amount idx
00: 67be8dddd2f94c0ecdc4426ba7b72dcd6da7eba97169f57d39aaa214a3e0d966 1.501568933000 1238243 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": 788156, "vin": [ { "gen": { "height": 788146 } } ], "vout": [ { "amount": 1501568933, "target": { "key": "67be8dddd2f94c0ecdc4426ba7b72dcd6da7eba97169f57d39aaa214a3e0d966" } } ], "extra": [ 1, 30, 93, 81, 48, 198, 226, 84, 24, 138, 253, 7, 163, 241, 100, 123, 62, 5, 2, 74, 11, 17, 245, 208, 234, 50, 243, 45, 11, 227, 145, 77, 149, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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