Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07570affb44c272c0788f1d9ebf8bc1f2042ff75c459a16250a00ad8b0b43828

Tx prefix hash: 9ea93c9bc0e43ac94a2959682a9765f71931d1d5f2648f95e564a4b050b570c1
Tx public key: 7009cb1f65878ea435a50092c3160a0dc8faddfb5bdc956986d5a737b26fb843
Timestamp: 1707784009 Timestamp [UCT]: 2024-02-13 00:26:49 Age [y:d:h:m:s]: 01:051:11:37:15
Block: 956275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297837 RingCT/type: yes/0
Extra: 017009cb1f65878ea435a50092c3160a0dc8faddfb5bdc956986d5a737b26fb8430211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb54d450e4e75d8e8789ce92ad7af38399e0c88cde53f0ca98ff4a72b711ad81 0.600000000000 1415579 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": 956285, "vin": [ { "gen": { "height": 956275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb54d450e4e75d8e8789ce92ad7af38399e0c88cde53f0ca98ff4a72b711ad81" } } ], "extra": [ 1, 112, 9, 203, 31, 101, 135, 142, 164, 53, 165, 0, 146, 195, 22, 10, 13, 200, 250, 221, 251, 91, 220, 149, 105, 134, 213, 167, 55, 178, 111, 184, 67, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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