Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0096e8a93c0e559dbefa8fa94f8629f70daf601c63e165c4511cc6a4ce4e9079

Tx prefix hash: 3aca3364a7ec2545b6b2a2a69e638cca46cb697d3488fa5dd29f3dbdc0516b08
Tx public key: b056c8ef583af244d21168dc82a648c5e3326d7857c9cb3843cee265bb233c91
Timestamp: 1727744475 Timestamp [UCT]: 2024-10-01 01:01:15 Age [y:d:h:m:s]: 00:115:02:34:40
Block: 1121765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82246 RingCT/type: yes/0
Extra: 01b056c8ef583af244d21168dc82a648c5e3326d7857c9cb3843cee265bb233c91021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef8bf959d47745d86b0999a080f06e3e432701a5f0adb4acc270e0eea591a1eb 0.600000000000 1604102 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": 1121775, "vin": [ { "gen": { "height": 1121765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef8bf959d47745d86b0999a080f06e3e432701a5f0adb4acc270e0eea591a1eb" } } ], "extra": [ 1, 176, 86, 200, 239, 88, 58, 242, 68, 210, 17, 104, 220, 130, 166, 72, 197, 227, 50, 109, 120, 87, 201, 203, 56, 67, 206, 226, 101, 187, 35, 60, 145, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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