Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b07e87bf4fdbff5b4911cd1210dcb366f59632f9aa9075dc1081d585ba69975b

Tx prefix hash: 4a2d41824fc64c571b7a038cb9a363559d3e8943664f4d2a91e79413d8b1c593
Tx public key: 7be04e953c67301978e0f143fa283641f35978ad9b77f7b1071a1978f6a8d4c8
Timestamp: 1722720093 Timestamp [UCT]: 2024-08-03 21:21:33 Age [y:d:h:m:s]: 00:173:10:55:26
Block: 1080105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124055 RingCT/type: yes/0
Extra: 017be04e953c67301978e0f143fa283641f35978ad9b77f7b1071a1978f6a8d4c8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ab4e9c02561c156c418eeba1a3d313d4b43eab5366b9bba202410ff5cf4b977 0.600000000000 1553336 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": 1080115, "vin": [ { "gen": { "height": 1080105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ab4e9c02561c156c418eeba1a3d313d4b43eab5366b9bba202410ff5cf4b977" } } ], "extra": [ 1, 123, 224, 78, 149, 60, 103, 48, 25, 120, 224, 241, 67, 250, 40, 54, 65, 243, 89, 120, 173, 155, 119, 247, 177, 7, 26, 25, 120, 246, 168, 212, 200, 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