Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e30b9bf792fdefdca72f2aea8d0ea9b283bd8fb48215a25294e2905afaa73441

Tx prefix hash: 79407f1d93ec9153b438f42b20a57779a1674aee30d3328b8ed687b7f125b393
Tx public key: a6a358a764fe3758683bbbc58344812ad2a0c836cd0c54d5421ff708a4a2d8bc
Timestamp: 1716429139 Timestamp [UCT]: 2024-05-23 01:52:19 Age [y:d:h:m:s]: 00:307:07:13:56
Block: 1027950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219624 RingCT/type: yes/0
Extra: 01a6a358a764fe3758683bbbc58344812ad2a0c836cd0c54d5421ff708a4a2d8bc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7188b273b8cf15153c2c98b904f5a6d04cbe3a377e9ef77587597e9a5b656303 0.600000000000 1495833 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": 1027960, "vin": [ { "gen": { "height": 1027950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7188b273b8cf15153c2c98b904f5a6d04cbe3a377e9ef77587597e9a5b656303" } } ], "extra": [ 1, 166, 163, 88, 167, 100, 254, 55, 88, 104, 59, 187, 197, 131, 68, 129, 42, 210, 160, 200, 54, 205, 12, 84, 213, 66, 31, 247, 8, 164, 162, 216, 188, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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