Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bc6c7a4d7d8facda602cc4673c989223600cbb388e144b1f23194841ee8c3a3

Tx prefix hash: 2ba1cd89e4fbb56da5b6959f505161e34afcad5a56925fea91465c3f85427244
Tx public key: 964549fdff3b0d3dc7b6f07a0aa60d3ceec240cf7b169d2b759c38ef49d86858
Timestamp: 1719831855 Timestamp [UCT]: 2024-07-01 11:04:15 Age [y:d:h:m:s]: 00:273:08:48:01
Block: 1056158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195323 RingCT/type: yes/0
Extra: 01964549fdff3b0d3dc7b6f07a0aa60d3ceec240cf7b169d2b759c38ef49d86858021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7acdeffd454c7eb3ab11a24a77f704fcfabdbcb5fab52ff107a86406e416ff4 0.600000000000 1526569 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": 1056168, "vin": [ { "gen": { "height": 1056158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7acdeffd454c7eb3ab11a24a77f704fcfabdbcb5fab52ff107a86406e416ff4" } } ], "extra": [ 1, 150, 69, 73, 253, 255, 59, 13, 61, 199, 182, 240, 122, 10, 166, 13, 60, 238, 194, 64, 207, 123, 22, 157, 43, 117, 156, 56, 239, 73, 216, 104, 88, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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