Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c370a7e5fd16c72e7d9fc03180c9f7d4487d9ac6c4e3d798302760fd61c44f47

Tx prefix hash: f8c673df7fe1ddca526a82b1794414fb226ab3bf9a9c7f7eea2f0db47bf04fa9
Tx public key: ddd0d128223b7aa1f7c81c49a08b838407593b75a0982275a9a9f8402f92cbf0
Timestamp: 1734978140 Timestamp [UCT]: 2024-12-23 18:22:20 Age [y:d:h:m:s]: 00:098:12:38:30
Block: 1181636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70177 RingCT/type: yes/0
Extra: 01ddd0d128223b7aa1f7c81c49a08b838407593b75a0982275a9a9f8402f92cbf002110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38bccfd919646163612a7baae83aecb9427f1b9dc509783eaf4b9161aae12ef5 0.600000000000 1668061 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": 1181646, "vin": [ { "gen": { "height": 1181636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38bccfd919646163612a7baae83aecb9427f1b9dc509783eaf4b9161aae12ef5" } } ], "extra": [ 1, 221, 208, 209, 40, 34, 59, 122, 161, 247, 200, 28, 73, 160, 139, 131, 132, 7, 89, 59, 117, 160, 152, 34, 117, 169, 169, 248, 64, 47, 146, 203, 240, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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