Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72db756d88349a2ac064aac2d2a9a8bfcc8bc354ce1bf7813b9d453fffd71b9

Tx prefix hash: 320719016b53754e077749aa1dc26c8fe27a6f18ff3d1af500b79efe5e44f0af
Tx public key: 4fc046cf094464cd99aa97ffa89ac793808229366f281286a82b7cb4abc42d2c
Timestamp: 1683470947 Timestamp [UCT]: 2023-05-07 14:49:07 Age [y:d:h:m:s]: 01:333:05:09:28
Block: 754969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499369 RingCT/type: yes/0
Extra: 014fc046cf094464cd99aa97ffa89ac793808229366f281286a82b7cb4abc42d2c021100000002e7ace25d000000000000000000

1 output(s) for total of 1.934080278000 dcy

stealth address amount amount idx
00: f7809c00c8890f2066eecbc9b4b9df9fba20d7ddcc40cc53c812d9ce9393fddb 1.934080278000 1203262 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": 754979, "vin": [ { "gen": { "height": 754969 } } ], "vout": [ { "amount": 1934080278, "target": { "key": "f7809c00c8890f2066eecbc9b4b9df9fba20d7ddcc40cc53c812d9ce9393fddb" } } ], "extra": [ 1, 79, 192, 70, 207, 9, 68, 100, 205, 153, 170, 151, 255, 168, 154, 199, 147, 128, 130, 41, 54, 111, 40, 18, 134, 168, 43, 124, 180, 171, 196, 45, 44, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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