Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4540f06d2d9859dd86477ee959a8c2d20f3693416182107072f9f268839547cd

Tx prefix hash: 910755a1ec7e12c0c3f2a2dc2995864decb696b56df733c2492a8dd4f4c4f8f7
Tx public key: 7f36e8f7eed1c6a355656b230031f8f50cc978831546f40ea4aaa01533d5d9ba
Timestamp: 1715315311 Timestamp [UCT]: 2024-05-10 04:28:31 Age [y:d:h:m:s]: 00:364:05:22:09
Block: 1018718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260363 RingCT/type: yes/0
Extra: 017f36e8f7eed1c6a355656b230031f8f50cc978831546f40ea4aaa01533d5d9ba0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79ce94568dc906b4f10f1639db4f119c8b567930e483feb1f7c46b07045823af 0.600000000000 1482511 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": 1018728, "vin": [ { "gen": { "height": 1018718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79ce94568dc906b4f10f1639db4f119c8b567930e483feb1f7c46b07045823af" } } ], "extra": [ 1, 127, 54, 232, 247, 238, 209, 198, 163, 85, 101, 107, 35, 0, 49, 248, 245, 12, 201, 120, 131, 21, 70, 244, 14, 164, 170, 160, 21, 51, 213, 217, 186, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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