Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c309a170de5e1493f9833b4050403dc766cdb6424a7d7cb3946a6399ca007d6

Tx prefix hash: 362e42c9dd3b2d6c8cb6076c53671e4c2c96ae0a603f7d14cfac6b9c7a5e1cd4
Tx public key: 05450928d7056f20bc84154b055a25250dc1cca7ea1f40773ca99f9f2e08b324
Timestamp: 1701102215 Timestamp [UCT]: 2023-11-27 16:23:35 Age [y:d:h:m:s]: 01:338:17:46:00
Block: 900887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500976 RingCT/type: yes/0
Extra: 0105450928d7056f20bc84154b055a25250dc1cca7ea1f40773ca99f9f2e08b32402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.635312463000 dcy

stealth address amount amount idx
00: 2dfc441679b2655225094a0d03a6e175815a5b37eba3454902a8c2fb733ce2cd 0.635312463000 1357414 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": 900897, "vin": [ { "gen": { "height": 900887 } } ], "vout": [ { "amount": 635312463, "target": { "key": "2dfc441679b2655225094a0d03a6e175815a5b37eba3454902a8c2fb733ce2cd" } } ], "extra": [ 1, 5, 69, 9, 40, 215, 5, 111, 32, 188, 132, 21, 75, 5, 90, 37, 37, 13, 193, 204, 167, 234, 31, 64, 119, 60, 169, 159, 159, 46, 8, 179, 36, 2, 17, 0, 0, 0, 1, 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