Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e256459ae024f475c14550163b5a37952f41db5fcad72a706e9e4fbd693e6d9

Tx prefix hash: 4c8e4894185ebd9d81548d7f0690246bf577e63a1ee86d3f1d286a32a47c04bf
Tx public key: 0bee16332f994b3a92c554aa47973eac1df100918e1f622eab5f9607dc9c2385
Timestamp: 1722240017 Timestamp [UCT]: 2024-07-29 08:00:17 Age [y:d:h:m:s]: 00:208:13:01:13
Block: 1076127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148912 RingCT/type: yes/0
Extra: 010bee16332f994b3a92c554aa47973eac1df100918e1f622eab5f9607dc9c238502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0de2b321c9ac46201169b30bc486247c4d60f3690589a84b1c827ec3947670f 0.600000000000 1548662 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": 1076137, "vin": [ { "gen": { "height": 1076127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0de2b321c9ac46201169b30bc486247c4d60f3690589a84b1c827ec3947670f" } } ], "extra": [ 1, 11, 238, 22, 51, 47, 153, 75, 58, 146, 197, 84, 170, 71, 151, 62, 172, 29, 241, 0, 145, 142, 31, 98, 46, 171, 95, 150, 7, 220, 156, 35, 133, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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