Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e828034ca1a88b19e0eab236e15ef0fccd2ea454e274e727d8abda41cbe2fbbf

Tx prefix hash: 7e42587e91e92989596a0d124c05c9527ab10256061711e8202a2b2802a15c9c
Tx public key: 0d6c85d657c4f37aaaa3996ac3f7968b282e13effed38a9d6b8487445c2ac261
Timestamp: 1577510002 Timestamp [UCT]: 2019-12-28 05:13:22 Age [y:d:h:m:s]: 05:002:19:01:07
Block: 33212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152145 RingCT/type: yes/0
Extra: 010d6c85d657c4f37aaaa3996ac3f7968b282e13effed38a9d6b8487445c2ac2610211000000179159db1e000000000000000000

1 output(s) for total of 476.382407209000 dcy

stealth address amount amount idx
00: 0b51f7230e7ce9beaa896b8adcdaea6143344554af011b53e73091b88a1d1316 476.382407209000 55545 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": 33222, "vin": [ { "gen": { "height": 33212 } } ], "vout": [ { "amount": 476382407209, "target": { "key": "0b51f7230e7ce9beaa896b8adcdaea6143344554af011b53e73091b88a1d1316" } } ], "extra": [ 1, 13, 108, 133, 214, 87, 196, 243, 122, 170, 163, 153, 106, 195, 247, 150, 139, 40, 46, 19, 239, 254, 211, 138, 157, 107, 132, 135, 68, 92, 42, 194, 97, 2, 17, 0, 0, 0, 23, 145, 89, 219, 30, 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