Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae636a30ca9ec7a374ef6ac8707433ca2152c802b9c4e9010be2085ed0c4bc7a

Tx prefix hash: ab3870427fb5fd43ec433105e7a2e96ad78471fcc65c743fc7fd14d3b075c42b
Tx public key: 9b7f1e8d87d2d22096d7ac1c58e0731925de9cf4f33f16c0fb90a096ef2445f8
Timestamp: 1697376971 Timestamp [UCT]: 2023-10-15 13:36:11 Age [y:d:h:m:s]: 01:245:15:01:03
Block: 870207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436501 RingCT/type: yes/0
Extra: 019b7f1e8d87d2d22096d7ac1c58e0731925de9cf4f33f16c0fb90a096ef2445f802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.802865869000 dcy

stealth address amount amount idx
00: e4bf533c8bd30e20295f533e8093b22adcc899010043e5a488639cd55170aa8a 0.802865869000 1325080 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": 870217, "vin": [ { "gen": { "height": 870207 } } ], "vout": [ { "amount": 802865869, "target": { "key": "e4bf533c8bd30e20295f533e8093b22adcc899010043e5a488639cd55170aa8a" } } ], "extra": [ 1, 155, 127, 30, 141, 135, 210, 210, 32, 150, 215, 172, 28, 88, 224, 115, 25, 37, 222, 156, 244, 243, 63, 22, 192, 251, 144, 160, 150, 239, 36, 69, 248, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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