Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db5e779a44d30bdb9d5f67fa6bc7c13e2c951d20fe38900d841d38d5b85aa7a6

Tx prefix hash: f7c96c6e053d1155acf5b734c552af1f7db4ab43c07da6f59686902ec215a1a4
Tx public key: 9db766f576a8263bd32ce5b0ef2b1a0557e5a7f6376ae961655f9b4b8c643db4
Timestamp: 1637082047 Timestamp [UCT]: 2021-11-16 17:00:47 Age [y:d:h:m:s]: 03:043:02:40:13
Block: 375660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 809555 RingCT/type: yes/0
Extra: 019db766f576a8263bd32ce5b0ef2b1a0557e5a7f6376ae961655f9b4b8c643db40211000000014a0f5013000000000000000000

1 output(s) for total of 34.936778955000 dcy

stealth address amount amount idx
00: 2ffedf0d60ef388f387347adc1fe89b840eb74d51700d5aed824c2d2bce256cc 34.936778955000 760032 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": 375670, "vin": [ { "gen": { "height": 375660 } } ], "vout": [ { "amount": 34936778955, "target": { "key": "2ffedf0d60ef388f387347adc1fe89b840eb74d51700d5aed824c2d2bce256cc" } } ], "extra": [ 1, 157, 183, 102, 245, 118, 168, 38, 59, 211, 44, 229, 176, 239, 43, 26, 5, 87, 229, 167, 246, 55, 106, 233, 97, 101, 95, 155, 75, 140, 100, 61, 180, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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