Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53edaaafec5249eb520c69f8df15630d5f9885df9d640b0bfa3af95a4b683fc2

Tx prefix hash: 4a6f6d6e7c05e66001a769b78e8dddc75710f4380dec37593de8b8d05aa87bc3
Tx public key: 1b144ef5c0be4d5ef6e328101fc30bdbdc8c0ef7f9591145f6309e337e04963a
Timestamp: 1732071373 Timestamp [UCT]: 2024-11-20 02:56:13 Age [y:d:h:m:s]: 00:004:03:33:54
Block: 1157533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2967 RingCT/type: yes/0
Extra: 011b144ef5c0be4d5ef6e328101fc30bdbdc8c0ef7f9591145f6309e337e04963a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4defc6b646c35c2829262e158e5dc32741b81a4ca661cdcf06d0af170e94d9c8 0.600000000000 1643156 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": 1157543, "vin": [ { "gen": { "height": 1157533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4defc6b646c35c2829262e158e5dc32741b81a4ca661cdcf06d0af170e94d9c8" } } ], "extra": [ 1, 27, 20, 78, 245, 192, 190, 77, 94, 246, 227, 40, 16, 31, 195, 11, 219, 220, 140, 14, 247, 249, 89, 17, 69, 246, 48, 158, 51, 126, 4, 150, 58, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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