Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78b15b4ba0f6ca6bbb8d2b3a46fc3d1c51474d7e316b4ffe14268bf90e19698

Tx prefix hash: d92047a0b311778afc7241384fcde9c4e10c54b13c4e6d99c6dbd505e4dfa33e
Tx public key: 77f9cdf9a32c8660f203a8a77cc90513c0fc24b3a00c1429db18a1b7e78a6ec8
Timestamp: 1701026795 Timestamp [UCT]: 2023-11-26 19:26:35 Age [y:d:h:m:s]: 01:088:20:41:05
Block: 900249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324639 RingCT/type: yes/0
Extra: 0177f9cdf9a32c8660f203a8a77cc90513c0fc24b3a00c1429db18a1b7e78a6ec802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.638412431000 dcy

stealth address amount amount idx
00: 0e1538d64b33237977b650a5ebe330af6c956bea781622a0da1bf840a6f17bf8 0.638412431000 1356736 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": 900259, "vin": [ { "gen": { "height": 900249 } } ], "vout": [ { "amount": 638412431, "target": { "key": "0e1538d64b33237977b650a5ebe330af6c956bea781622a0da1bf840a6f17bf8" } } ], "extra": [ 1, 119, 249, 205, 249, 163, 44, 134, 96, 242, 3, 168, 167, 124, 201, 5, 19, 192, 252, 36, 179, 160, 12, 20, 41, 219, 24, 161, 183, 231, 138, 110, 200, 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