Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fb2013d90ad3980ee74d37ade80c4e982fa4111fbcc9427c1e342d4f28267c2

Tx prefix hash: 4857c405fb1bea5212999c62ec9706a3a625569e99776fa38a57e4c1979542ed
Tx public key: 71c6ac8199a5948431714ce93a734dcaf8c9b928346e661b27edd0d2ce7605fb
Timestamp: 1703846669 Timestamp [UCT]: 2023-12-29 10:44:29 Age [y:d:h:m:s]: 01:313:20:55:37
Block: 923633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483155 RingCT/type: yes/0
Extra: 0171c6ac8199a5948431714ce93a734dcaf8c9b928346e661b27edd0d2ce7605fb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9e1664d41d81bf6a97e840f40b6da1563bd3aa48dcaae1b5f5867f7b6b85b5b 0.600000000000 1381367 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": 923643, "vin": [ { "gen": { "height": 923633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9e1664d41d81bf6a97e840f40b6da1563bd3aa48dcaae1b5f5867f7b6b85b5b" } } ], "extra": [ 1, 113, 198, 172, 129, 153, 165, 148, 132, 49, 113, 76, 233, 58, 115, 77, 202, 248, 201, 185, 40, 52, 110, 102, 27, 39, 237, 208, 210, 206, 118, 5, 251, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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