Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2b20b04723367ba8a3f88ba6060b58618bfb4f4f7a797f8e5125c08c14594b7

Tx prefix hash: c1510c6a939e1ac3a0a74930e2d5862e7c756266fc0c2206f2b9a4751315d06f
Tx public key: 9f10175789e4e890c4eeb5b60486257557fe43fbee221f0cccddf0e607e2cc4d
Timestamp: 1721883029 Timestamp [UCT]: 2024-07-25 04:50:29 Age [y:d:h:m:s]: 00:267:04:22:11
Block: 1073158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190884 RingCT/type: yes/0
Extra: 019f10175789e4e890c4eeb5b60486257557fe43fbee221f0cccddf0e607e2cc4d02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd3680ee39cfbc7324f3395159f8eeb59a0efc6505a175391bc28294d0de0ec2 0.600000000000 1545657 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": 1073168, "vin": [ { "gen": { "height": 1073158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd3680ee39cfbc7324f3395159f8eeb59a0efc6505a175391bc28294d0de0ec2" } } ], "extra": [ 1, 159, 16, 23, 87, 137, 228, 232, 144, 196, 238, 181, 182, 4, 134, 37, 117, 87, 254, 67, 251, 238, 34, 31, 12, 204, 221, 240, 230, 7, 226, 204, 77, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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