Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923fd9e885368e13596f209cc2f5200fccb944a26da78e5adfbdf10a4541da26

Tx prefix hash: 191cf768f095eb1a605ff11cde82c879b7d6c483ac630190dabe0aa27e3756d9
Tx public key: 34138c61f2d0a818e0567a5dc481808f4a3ec03d2dfef92ccb5cf930183d842e
Timestamp: 1673186780 Timestamp [UCT]: 2023-01-08 14:06:20 Age [y:d:h:m:s]: 02:089:11:39:24
Block: 670296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 585640 RingCT/type: yes/0
Extra: 0134138c61f2d0a818e0567a5dc481808f4a3ec03d2dfef92ccb5cf930183d842e02110000000152542ceb000000000000000000

1 output(s) for total of 3.690039845000 dcy

stealth address amount amount idx
00: e9e6f3c8fa44d5f87a7a427d2eead6b64d0201838f9f177b99ba621dad2cc016 3.690039845000 1111687 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": 670306, "vin": [ { "gen": { "height": 670296 } } ], "vout": [ { "amount": 3690039845, "target": { "key": "e9e6f3c8fa44d5f87a7a427d2eead6b64d0201838f9f177b99ba621dad2cc016" } } ], "extra": [ 1, 52, 19, 140, 97, 242, 208, 168, 24, 224, 86, 122, 93, 196, 129, 128, 143, 74, 62, 192, 61, 45, 254, 249, 44, 203, 92, 249, 48, 24, 61, 132, 46, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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