Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85c9c95ba0df935e254013c11460f77006c58150acfa3a4f29d5bdf5dd7ca53

Tx prefix hash: 799403d0808ec9a3f38f36ed3caee41cd8b16e5cf4ea7565030a71ea07f13b5f
Tx public key: 702e276f778c61237a90e82466c50d05d8bc002e27cf72d19d808644283c9714
Timestamp: 1639226976 Timestamp [UCT]: 2021-12-11 12:49:36 Age [y:d:h:m:s]: 03:058:10:04:03
Block: 393200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 820474 RingCT/type: yes/0
Extra: 01702e276f778c61237a90e82466c50d05d8bc002e27cf72d19d808644283c971402110000000d06faf294000000000000000000

1 output(s) for total of 30.560857532000 dcy

stealth address amount amount idx
00: f70387cab4126ee425bcaa134049b34f1d6d12a6d1238f6a238244edbf800ab9 30.560857532000 790371 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": 393210, "vin": [ { "gen": { "height": 393200 } } ], "vout": [ { "amount": 30560857532, "target": { "key": "f70387cab4126ee425bcaa134049b34f1d6d12a6d1238f6a238244edbf800ab9" } } ], "extra": [ 1, 112, 46, 39, 111, 119, 140, 97, 35, 122, 144, 232, 36, 102, 197, 13, 5, 216, 188, 0, 46, 39, 207, 114, 209, 157, 128, 134, 68, 40, 60, 151, 20, 2, 17, 0, 0, 0, 13, 6, 250, 242, 148, 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