Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded4647f1b759bd7a7e264e72646c35cb230cd60963230be4776220c19f3f40f

Tx prefix hash: 2fc772c7f46da8b8b73c4eed1ef741421e38dc8fdba942d99ee43b604b109d67
Tx public key: 34c0fb158e0edf230efac862f47c2792309f59163849d3d9fad5a3c1df0673f4
Timestamp: 1718889220 Timestamp [UCT]: 2024-06-20 13:13:40 Age [y:d:h:m:s]: 00:269:23:17:14
Block: 1048349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192920 RingCT/type: yes/0
Extra: 0134c0fb158e0edf230efac862f47c2792309f59163849d3d9fad5a3c1df0673f40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a876664efbce2925f5bdec298532e4b529ac3fdc52e6fa4b91b429bdad69d703 0.600000000000 1518414 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": 1048359, "vin": [ { "gen": { "height": 1048349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a876664efbce2925f5bdec298532e4b529ac3fdc52e6fa4b91b429bdad69d703" } } ], "extra": [ 1, 52, 192, 251, 21, 142, 14, 223, 35, 14, 250, 200, 98, 244, 124, 39, 146, 48, 159, 89, 22, 56, 73, 211, 217, 250, 213, 163, 193, 223, 6, 115, 244, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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