Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50907bf71ad5fc0331249e9cb965c24fd40c763ab97cbb8cf2c1a1f637374b31

Tx prefix hash: 1dadc860c851500673c957cda0e57b31bf3fd6eb68e9aa7a86e26041c26a8f9c
Tx public key: d27733f4bc92e53741d3729958832050c1583f3e9bdbb2561c00f04aed439b77
Timestamp: 1729097271 Timestamp [UCT]: 2024-10-16 16:47:51 Age [y:d:h:m:s]: 00:159:03:34:04
Block: 1132979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113505 RingCT/type: yes/0
Extra: 01d27733f4bc92e53741d3729958832050c1583f3e9bdbb2561c00f04aed439b77021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 836f0529013c671dc498a46b399d10ec61b58f6cf1547bd6c4a0b74bfd4e084e 0.600000000000 1616032 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": 1132989, "vin": [ { "gen": { "height": 1132979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "836f0529013c671dc498a46b399d10ec61b58f6cf1547bd6c4a0b74bfd4e084e" } } ], "extra": [ 1, 210, 119, 51, 244, 188, 146, 229, 55, 65, 211, 114, 153, 88, 131, 32, 80, 193, 88, 63, 62, 155, 219, 178, 86, 28, 0, 240, 74, 237, 67, 155, 119, 2, 17, 0, 0, 0, 4, 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