Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65c4c91d08e0fa2565d72b99c73ecc5adb82407448acf15b22aa2586b4594533

Tx prefix hash: a22c5ce79354d754974ae1dcb046cda04b2f5dfb2e275102089c54d63c37b61e
Tx public key: 1fc29ad625c1fef20908f03c5d004d2df009ee8eb9814c0cfb0f121ed3da572f
Timestamp: 1733481407 Timestamp [UCT]: 2024-12-06 10:36:47 Age [y:d:h:m:s]: 00:123:02:59:02
Block: 1169222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87788 RingCT/type: yes/0
Extra: 011fc29ad625c1fef20908f03c5d004d2df009ee8eb9814c0cfb0f121ed3da572f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6631eed1e2422f492e21017b8eb269c9309a611dc54380ee85e7abc7cefbf61d 0.600000000000 1654937 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": 1169232, "vin": [ { "gen": { "height": 1169222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6631eed1e2422f492e21017b8eb269c9309a611dc54380ee85e7abc7cefbf61d" } } ], "extra": [ 1, 31, 194, 154, 214, 37, 193, 254, 242, 9, 8, 240, 60, 93, 0, 77, 45, 240, 9, 238, 142, 185, 129, 76, 12, 251, 15, 18, 30, 211, 218, 87, 47, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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