Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0396fdffabc9e3664e1739f7372ba1a205f55517655ea93e277d569dc6de527

Tx prefix hash: fbe98bad9b79743579af4016945025ace279d6b91d361e4a4c85827ad83425d5
Tx public key: 12b89d8a876be8e042d71820f2fc1b85293142e6a1e082785196cdb591ccd70b
Timestamp: 1721211847 Timestamp [UCT]: 2024-07-17 10:24:07 Age [y:d:h:m:s]: 00:259:22:35:30
Block: 1067611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185685 RingCT/type: yes/0
Extra: 0112b89d8a876be8e042d71820f2fc1b85293142e6a1e082785196cdb591ccd70b02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0040fcb91f1f2aa7ceda4dbe63bf49a8aa34d54ce74bed3628c485a8ba7feb7e 0.600000000000 1538468 of 15

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": 1067621, "vin": [ { "gen": { "height": 1067611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0040fcb91f1f2aa7ceda4dbe63bf49a8aa34d54ce74bed3628c485a8ba7feb7e" } } ], "extra": [ 1, 18, 184, 157, 138, 135, 107, 232, 224, 66, 215, 24, 32, 242, 252, 27, 133, 41, 49, 66, 230, 161, 224, 130, 120, 81, 150, 205, 181, 145, 204, 215, 11, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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