Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6645812944cd75f218a2750583ebacf1ce3c408e18a1ec21b3edfd0ed78edcc4

Tx prefix hash: 71c0c276555804a3eeea28fcdd39ab9b38b4e1b8d3a4e85b0f3d15ab6b1ea785
Tx public key: 8aee080be5922daf953073d5d2909129f7946451181b856bd3b81c0184f69be0
Timestamp: 1694153747 Timestamp [UCT]: 2023-09-08 06:15:47 Age [y:d:h:m:s]: 01:249:14:05:14
Block: 843456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439524 RingCT/type: yes/0
Extra: 018aee080be5922daf953073d5d2909129f7946451181b856bd3b81c0184f69be002110000000333af99f4000000000000000000

1 output(s) for total of 0.984646186000 dcy

stealth address amount amount idx
00: 86c770ad2acd0dea6b0bb848ad22dd2021d9b3bc036dee2492f5d611e6c0412f 0.984646186000 1296688 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": 843466, "vin": [ { "gen": { "height": 843456 } } ], "vout": [ { "amount": 984646186, "target": { "key": "86c770ad2acd0dea6b0bb848ad22dd2021d9b3bc036dee2492f5d611e6c0412f" } } ], "extra": [ 1, 138, 238, 8, 11, 229, 146, 45, 175, 149, 48, 115, 213, 210, 144, 145, 41, 247, 148, 100, 81, 24, 27, 133, 107, 211, 184, 28, 1, 132, 246, 155, 224, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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