Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f92f1fe5d67a703415f20057ce988a2875f61ff11a62568ee128dc8ad908a1

Tx prefix hash: 8f541db4c8edfe7930badbdd3062eb0fc7f4ad327511ce628f5718a854e57709
Tx public key: 7f97e57402e26bb5e7f5935bfcdc208b95a4f53c63a0b7728cc5376541cf6ff7
Timestamp: 1650140525 Timestamp [UCT]: 2022-04-16 20:22:05 Age [y:d:h:m:s]: 03:198:20:07:30
Block: 481641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 920408 RingCT/type: yes/0
Extra: 017f97e57402e26bb5e7f5935bfcdc208b95a4f53c63a0b7728cc5376541cf6ff702110000000fe6d27f9c000000000000000000

1 output(s) for total of 15.564087393000 dcy

stealth address amount amount idx
00: 0b1a7e9998312ea8ee2605af1a5678c98db93a84d6d84a463ab2ae1c3b084c06 15.564087393000 902962 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": 481651, "vin": [ { "gen": { "height": 481641 } } ], "vout": [ { "amount": 15564087393, "target": { "key": "0b1a7e9998312ea8ee2605af1a5678c98db93a84d6d84a463ab2ae1c3b084c06" } } ], "extra": [ 1, 127, 151, 229, 116, 2, 226, 107, 181, 231, 245, 147, 91, 252, 220, 32, 139, 149, 164, 245, 60, 99, 160, 183, 114, 140, 197, 55, 101, 65, 207, 111, 247, 2, 17, 0, 0, 0, 15, 230, 210, 127, 156, 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