Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f424127353b4631a0165d7b7e646170f6430ef13746d67c40fdc2d2767b3bd37

Tx prefix hash: bc68c4b2b9ce2215323811f5998dddfe3a51f4f5c9160bf7f15c5d300226ce44
Tx public key: e016138a953e4b73fdefb3dc36ef60af929608bea988e42032505ea164fdbd2d
Timestamp: 1730358347 Timestamp [UCT]: 2024-10-31 07:05:47 Age [y:d:h:m:s]: 00:143:01:43:07
Block: 1143354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102081 RingCT/type: yes/0
Extra: 01e016138a953e4b73fdefb3dc36ef60af929608bea988e42032505ea164fdbd2d021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b31d7b54e02e6988ab661094df5bbe1fc8369cfa70bec263b61484d2b29ff8a2 0.600000000000 1627217 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": 1143364, "vin": [ { "gen": { "height": 1143354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b31d7b54e02e6988ab661094df5bbe1fc8369cfa70bec263b61484d2b29ff8a2" } } ], "extra": [ 1, 224, 22, 19, 138, 149, 62, 75, 115, 253, 239, 179, 220, 54, 239, 96, 175, 146, 150, 8, 190, 169, 136, 228, 32, 50, 80, 94, 161, 100, 253, 189, 45, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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