Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eb3dcf03eda4f06472a2e514059e15dd9f67f348d3803832b9b5a1913baa180

Tx prefix hash: fe02de4156a848fb4a40903145af9b0cd8ca7b82e96cb9e72420163aafd46d63
Tx public key: 867807f7c391772763e0e5664654a91720c5a90d3f2813ebfcf6daa706df5ae1
Timestamp: 1717993215 Timestamp [UCT]: 2024-06-10 04:20:15 Age [y:d:h:m:s]: 00:304:08:16:23
Block: 1040923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217498 RingCT/type: yes/0
Extra: 01867807f7c391772763e0e5664654a91720c5a90d3f2813ebfcf6daa706df5ae1021100000006d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93a37d22ebc2d8ce83770c435531bb04fc3c7d3a91691c1d57ce96e0b941f665 0.600000000000 1509586 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": 1040933, "vin": [ { "gen": { "height": 1040923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93a37d22ebc2d8ce83770c435531bb04fc3c7d3a91691c1d57ce96e0b941f665" } } ], "extra": [ 1, 134, 120, 7, 247, 195, 145, 119, 39, 99, 224, 229, 102, 70, 84, 169, 23, 32, 197, 169, 13, 63, 40, 19, 235, 252, 246, 218, 167, 6, 223, 90, 225, 2, 17, 0, 0, 0, 6, 215, 73, 245, 17, 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