Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e8e82a1f30ac97bdba23d45d1774e73cb95e3cb550b66f5310ddb3da110f958

Tx prefix hash: 358966473817bc7735e3d3b7819dae8e026459d31b7b47aa469a68be1f0c95ec
Tx public key: b23942f7bced3393be1708960fafeb3c2e68330f01f059f5fd88261ccbb1a5a3
Timestamp: 1742609619 Timestamp [UCT]: 2025-03-22 02:13:39 Age [y:d:h:m:s]: 00:289:19:54:53
Block: 1244520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204962 RingCT/type: yes/0
Extra: 01b23942f7bced3393be1708960fafeb3c2e68330f01f059f5fd88261ccbb1a5a302110000000aca0c97f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a19cee7c78135441f4d92cfaec5443f0a06086e5017706290bfe9b00396a5c47 0.600000000000 1731511 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": 1244530, "vin": [ { "gen": { "height": 1244520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a19cee7c78135441f4d92cfaec5443f0a06086e5017706290bfe9b00396a5c47" } } ], "extra": [ 1, 178, 57, 66, 247, 188, 237, 51, 147, 190, 23, 8, 150, 15, 175, 235, 60, 46, 104, 51, 15, 1, 240, 89, 245, 253, 136, 38, 28, 203, 177, 165, 163, 2, 17, 0, 0, 0, 10, 202, 12, 151, 245, 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