Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd4340b239d196183e2e96b6b6d836ee58275ca654f2184f877438e26d0f3f79

Tx prefix hash: 6536d671f545ba766cf25b6fff4da9d5983a122d2727ca7cf3f247265f4340b8
Tx public key: 440bf35a690b5de8ea4b76762914fbde0bb689d3d66541f85276d2a6f3b74c85
Timestamp: 1694013616 Timestamp [UCT]: 2023-09-06 15:20:16 Age [y:d:h:m:s]: 01:134:03:57:52
Block: 842298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357223 RingCT/type: yes/0
Extra: 01440bf35a690b5de8ea4b76762914fbde0bb689d3d66541f85276d2a6f3b74c8502110000000233af99f4000000000000000000

1 output(s) for total of 0.993383951000 dcy

stealth address amount amount idx
00: 9d9ad70fb89b75db60d115554b9f1105f04591de40d2824a74979382a3993541 0.993383951000 1295408 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": 842308, "vin": [ { "gen": { "height": 842298 } } ], "vout": [ { "amount": 993383951, "target": { "key": "9d9ad70fb89b75db60d115554b9f1105f04591de40d2824a74979382a3993541" } } ], "extra": [ 1, 68, 11, 243, 90, 105, 11, 93, 232, 234, 75, 118, 118, 41, 20, 251, 222, 11, 182, 137, 211, 214, 101, 65, 248, 82, 118, 210, 166, 243, 183, 76, 133, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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