Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2515f9fea2984306e5fe8fa9e40c53d8bf11689b521a7db8f8659b837d7b677f

Tx prefix hash: 36a9e3b065b1fd0d4d51a4d96b19327a47b86160a0b03224b6e5e9fe8ef8de24
Tx public key: 050b99a707c19e927ef51b47a05e79b900ae7e256c1aae6fc8b0adc07986331b
Timestamp: 1699360079 Timestamp [UCT]: 2023-11-07 12:27:59 Age [y:d:h:m:s]: 01:188:21:06:38
Block: 886443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396210 RingCT/type: yes/0
Extra: 01050b99a707c19e927ef51b47a05e79b900ae7e256c1aae6fc8b0adc07986331b02110000000833af99f4000000000000000000

1 output(s) for total of 0.709326793000 dcy

stealth address amount amount idx
00: fca333a7276ec5ea0f00272f4aae1e162664d1d2615acaee8d9217bd715adea5 0.709326793000 1342262 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": 886453, "vin": [ { "gen": { "height": 886443 } } ], "vout": [ { "amount": 709326793, "target": { "key": "fca333a7276ec5ea0f00272f4aae1e162664d1d2615acaee8d9217bd715adea5" } } ], "extra": [ 1, 5, 11, 153, 167, 7, 193, 158, 146, 126, 245, 27, 71, 160, 94, 121, 185, 0, 174, 126, 37, 108, 26, 174, 111, 200, 176, 173, 192, 121, 134, 51, 27, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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