Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33ed5d0d4959778bd78bcae16559417e2741494d6f7dae72001fedc6f554f446

Tx prefix hash: cf4c326fd10abb3ba7a5d66e2fff3d2d14b6a44592d0cd1c17f5ecf89f4a7562
Tx public key: 4b675770dd65c4c3ee7de47e3cd943ab18fe90682d4607a6646ef9bd4c18b4e8
Timestamp: 1727193692 Timestamp [UCT]: 2024-09-24 16:01:32 Age [y:d:h:m:s]: 00:205:22:45:58
Block: 1117195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147018 RingCT/type: yes/0
Extra: 014b675770dd65c4c3ee7de47e3cd943ab18fe90682d4607a6646ef9bd4c18b4e8021100000008e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: db390b56f4deaeaa474bfe3bb098614bc14fba70ef979c67474f82f8d4241ff7 0.608000000000 1597942 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": 1117205, "vin": [ { "gen": { "height": 1117195 } } ], "vout": [ { "amount": 608000000, "target": { "key": "db390b56f4deaeaa474bfe3bb098614bc14fba70ef979c67474f82f8d4241ff7" } } ], "extra": [ 1, 75, 103, 87, 112, 221, 101, 196, 195, 238, 125, 228, 126, 60, 217, 67, 171, 24, 254, 144, 104, 45, 70, 7, 166, 100, 110, 249, 189, 76, 24, 180, 232, 2, 17, 0, 0, 0, 8, 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