Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d849509a0128f07b1a83319aca5ce84f29bc277a3752d2f0fab6806ceafc700a

Tx prefix hash: 967fc797efc85cb1270b48b830f44488937a98c445f87c4caa6d136fe1fc9f53
Tx public key: a61a8a21a53a4c7c6ddd591ce13eb9ed5e249edcc176923430fffbbde3da778b
Timestamp: 1578537247 Timestamp [UCT]: 2020-01-09 02:34:07 Age [y:d:h:m:s]: 05:012:11:08:18
Block: 41724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159016 RingCT/type: yes/0
Extra: 01a61a8a21a53a4c7c6ddd591ce13eb9ed5e249edcc176923430fffbbde3da778b02110000000f4ac5aa02000000000000000000

1 output(s) for total of 446.428500486000 dcy

stealth address amount amount idx
00: 82ddf01aa07eb7a129cef6b6620f1dd172e5535135597b969f864f4e190ccfaa 446.428500486000 74631 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": 41734, "vin": [ { "gen": { "height": 41724 } } ], "vout": [ { "amount": 446428500486, "target": { "key": "82ddf01aa07eb7a129cef6b6620f1dd172e5535135597b969f864f4e190ccfaa" } } ], "extra": [ 1, 166, 26, 138, 33, 165, 58, 76, 124, 109, 221, 89, 28, 225, 62, 185, 237, 94, 36, 158, 220, 193, 118, 146, 52, 48, 255, 251, 189, 227, 218, 119, 139, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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