Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c61074ed647145603cc061d1d8445164bdcb56326e0a601294029940c94fa45

Tx prefix hash: 3ce7c3c33a04e406808d8841fa325a0e6fc68ac94069b5c7e017c2e7b7736c9b
Tx public key: 58d5009df190f9201116f4bd6fbfff638549937f30af7ee83c0664d99be4d70e
Timestamp: 1699689568 Timestamp [UCT]: 2023-11-11 07:59:28 Age [y:d:h:m:s]: 01:089:08:18:32
Block: 889178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325014 RingCT/type: yes/0
Extra: 0158d5009df190f9201116f4bd6fbfff638549937f30af7ee83c0664d99be4d70e021100000003faf35c9c000000000000000000

1 output(s) for total of 0.694708999000 dcy

stealth address amount amount idx
00: d5c31f0b36322842593676e6ce3c61e2da1afaadd345bb3c3c839a6641ca285d 0.694708999000 1345155 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": 889188, "vin": [ { "gen": { "height": 889178 } } ], "vout": [ { "amount": 694708999, "target": { "key": "d5c31f0b36322842593676e6ce3c61e2da1afaadd345bb3c3c839a6641ca285d" } } ], "extra": [ 1, 88, 213, 0, 157, 241, 144, 249, 32, 17, 22, 244, 189, 111, 191, 255, 99, 133, 73, 147, 127, 48, 175, 126, 232, 60, 6, 100, 217, 155, 228, 215, 14, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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