Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97a645d30c72e4c9597956748e1139bfd7f1a5fee10613b207b66d59b599af0a

Tx prefix hash: 64d85f6f4d6ea4e8ce375be9de43081e55dffd2dc856d81722d52be011e88d50
Tx public key: 44b77ff8fce71ab0a5e5119c16cf395ceffce58b44f90a655303f4b3ff03f84c
Timestamp: 1717392220 Timestamp [UCT]: 2024-06-03 05:23:40 Age [y:d:h:m:s]: 01:013:06:01:07
Block: 1035948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270259 RingCT/type: yes/0
Extra: 0144b77ff8fce71ab0a5e5119c16cf395ceffce58b44f90a655303f4b3ff03f84c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48bb56663cb468a4c15e9451116aaa067f0d51f00420a32e8ce5ad3e867efc2c 0.600000000000 1504473 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": 1035958, "vin": [ { "gen": { "height": 1035948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48bb56663cb468a4c15e9451116aaa067f0d51f00420a32e8ce5ad3e867efc2c" } } ], "extra": [ 1, 68, 183, 127, 248, 252, 231, 26, 176, 165, 229, 17, 156, 22, 207, 57, 92, 239, 252, 229, 139, 68, 249, 10, 101, 83, 3, 244, 179, 255, 3, 248, 76, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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