Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79ac50966c9fef325599b00330ef3a37016d4e16456cf1e2d15e967694f21b84

Tx prefix hash: a2466cc86daffe0780849e256577ee3238f176a4ecde1ab0e55f2fe225273e67
Tx public key: f8b1c266f87c2574ee76cddad066bf5b2a1c6a8cae1b2b74d8f1a947a96f230e
Timestamp: 1710122549 Timestamp [UCT]: 2024-03-11 02:02:29 Age [y:d:h:m:s]: 00:350:05:15:22
Block: 975676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250383 RingCT/type: yes/0
Extra: 01f8b1c266f87c2574ee76cddad066bf5b2a1c6a8cae1b2b74d8f1a947a96f230e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7477f2e251ac81df7c3c1e32f1e5d58805be6ed5bf788c7113c91375daf95dc2 0.600000000000 1435649 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": 975686, "vin": [ { "gen": { "height": 975676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7477f2e251ac81df7c3c1e32f1e5d58805be6ed5bf788c7113c91375daf95dc2" } } ], "extra": [ 1, 248, 177, 194, 102, 248, 124, 37, 116, 238, 118, 205, 218, 208, 102, 191, 91, 42, 28, 106, 140, 174, 27, 43, 116, 216, 241, 169, 71, 169, 111, 35, 14, 2, 17, 0, 0, 0, 6, 89, 218, 211, 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