Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbe7923444cc9dd851692d997a733e33bf4d187a7521fd8ddf24a985d9c95fd0

Tx prefix hash: fd0be830f12ef0ad0c7e5f0c5145be3fdd89c71a0090ee607cf18eac2557ea8b
Tx public key: 4d9b4c81e83967503de206eda3d1af44fe355b42e302297c25b03d09ceee1da6
Timestamp: 1701448926 Timestamp [UCT]: 2023-12-01 16:42:06 Age [y:d:h:m:s]: 01:353:21:54:44
Block: 903749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511834 RingCT/type: yes/0
Extra: 014d9b4c81e83967503de206eda3d1af44fe355b42e302297c25b03d09ceee1da602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.621590512000 dcy

stealth address amount amount idx
00: 6199a131e2cd63f3e266643866f1624aaeabf054694509cbda6a2f66c1fcea61 0.621590512000 1360440 of 0

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": 903759, "vin": [ { "gen": { "height": 903749 } } ], "vout": [ { "amount": 621590512, "target": { "key": "6199a131e2cd63f3e266643866f1624aaeabf054694509cbda6a2f66c1fcea61" } } ], "extra": [ 1, 77, 155, 76, 129, 232, 57, 103, 80, 61, 226, 6, 237, 163, 209, 175, 68, 254, 53, 91, 66, 227, 2, 41, 124, 37, 176, 61, 9, 206, 238, 29, 166, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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