Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4083c3dc0e87d112c88db258f2cb0f9d730a54f34ff904f7a75d4df467d4d3a

Tx prefix hash: 39f1d9c9235c62c99f166e8108fa1ae844c82c732807ba33b9c29a1443c3127a
Tx public key: 52fb1bcdcee3406eb3a22695795932bbf01c3b5586dc07df554d026bb64689e4
Timestamp: 1635352426 Timestamp [UCT]: 2021-10-27 16:33:46 Age [y:d:h:m:s]: 03:080:15:05:08
Block: 361659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 836075 RingCT/type: yes/0
Extra: 0152fb1bcdcee3406eb3a22695795932bbf01c3b5586dc07df554d026bb64689e402110000001342b3953e000000000000000000

1 output(s) for total of 38.875322757000 dcy

stealth address amount amount idx
00: cc3b3f7cb5eb3892e1514537ddd132ba2afb93dc9d56971fe9a35f5720e74f41 38.875322757000 735705 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": 361669, "vin": [ { "gen": { "height": 361659 } } ], "vout": [ { "amount": 38875322757, "target": { "key": "cc3b3f7cb5eb3892e1514537ddd132ba2afb93dc9d56971fe9a35f5720e74f41" } } ], "extra": [ 1, 82, 251, 27, 205, 206, 227, 64, 110, 179, 162, 38, 149, 121, 89, 50, 187, 240, 28, 59, 85, 134, 220, 7, 223, 85, 77, 2, 107, 182, 70, 137, 228, 2, 17, 0, 0, 0, 19, 66, 179, 149, 62, 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