Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af925b4d8721b4a481bd2937925c73bc12eb2876ffa5efa09b05afc56b5a9e94

Tx prefix hash: d0bd15d3263469e56b7c45bbe1bf444a40c0256b83ab6268572bd19b721660e4
Tx public key: 92c7d5fc8dfced07e4373e02903e8c1c8a61caaa99d27c2180fa2a189242e79a
Timestamp: 1704793146 Timestamp [UCT]: 2024-01-09 09:39:06 Age [y:d:h:m:s]: 01:083:17:26:13
Block: 931469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320929 RingCT/type: yes/0
Extra: 0192c7d5fc8dfced07e4373e02903e8c1c8a61caaa99d27c2180fa2a189242e79a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb33e1a7a297db939538f6865325d6728c03753ccff0b76a8c38e5961122c818 0.600000000000 1389371 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": 931479, "vin": [ { "gen": { "height": 931469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb33e1a7a297db939538f6865325d6728c03753ccff0b76a8c38e5961122c818" } } ], "extra": [ 1, 146, 199, 213, 252, 141, 252, 237, 7, 228, 55, 62, 2, 144, 62, 140, 28, 138, 97, 202, 170, 153, 210, 124, 33, 128, 250, 42, 24, 146, 66, 231, 154, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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