Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f48af5f76ff5423a2da35730a288b6a1488a37e07a85d56dc583c3060bf32b0

Tx prefix hash: fa09002912b65bfb014d20eeed45fab035e285f831f99ce4589d4a1f4e61234a
Tx public key: 4deb01759233b20440325a42aaae3a0a9f6fcc1220586677f22015266ea1264f
Timestamp: 1577381498 Timestamp [UCT]: 2019-12-26 17:31:38 Age [y:d:h:m:s]: 05:123:23:22:51
Block: 32359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1238351 RingCT/type: yes/0
Extra: 014deb01759233b20440325a42aaae3a0a9f6fcc1220586677f22015266ea1264f021100000096c3a1a09f000000000000000000

1 output(s) for total of 479.492765466000 dcy

stealth address amount amount idx
00: e40a6eac31f4a805d209ffaa2e26417dcdb5487d7d1727e8ea3d63fcf33a99bf 479.492765466000 53793 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": 32369, "vin": [ { "gen": { "height": 32359 } } ], "vout": [ { "amount": 479492765466, "target": { "key": "e40a6eac31f4a805d209ffaa2e26417dcdb5487d7d1727e8ea3d63fcf33a99bf" } } ], "extra": [ 1, 77, 235, 1, 117, 146, 51, 178, 4, 64, 50, 90, 66, 170, 174, 58, 10, 159, 111, 204, 18, 32, 88, 102, 119, 242, 32, 21, 38, 110, 161, 38, 79, 2, 17, 0, 0, 0, 150, 195, 161, 160, 159, 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