Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78e1fcd8f57860b0a2b62a38e8a5c2473e9ee76062cacf860e35268959ae2e88

Tx prefix hash: 33509dfac854237612848e2a8fa4528e112f7f15d82ca7afdc0ef22d51d88b60
Tx public key: 3deeae739520b01eebf5cf41ca0fa4bea542c36c699cf5fddf3c9766e370401c
Timestamp: 1632779717 Timestamp [UCT]: 2021-09-27 21:55:17 Age [y:d:h:m:s]: 03:213:14:54:03
Block: 342107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 929201 RingCT/type: yes/0
Extra: 013deeae739520b01eebf5cf41ca0fa4bea542c36c699cf5fddf3c9766e370401c02110000000ef29d7abf000000000000000000

1 output(s) for total of 45.129230173000 dcy

stealth address amount amount idx
00: 7f47770b53532915e3683de64bbb2cf073d46c6a6b2acceb89f59f77342cc354 45.129230173000 702647 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": 342117, "vin": [ { "gen": { "height": 342107 } } ], "vout": [ { "amount": 45129230173, "target": { "key": "7f47770b53532915e3683de64bbb2cf073d46c6a6b2acceb89f59f77342cc354" } } ], "extra": [ 1, 61, 238, 174, 115, 149, 32, 176, 30, 235, 245, 207, 65, 202, 15, 164, 190, 165, 66, 195, 108, 105, 156, 245, 253, 223, 60, 151, 102, 227, 112, 64, 28, 2, 17, 0, 0, 0, 14, 242, 157, 122, 191, 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