Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7067641ecbd9589320b93a90fe3fec38a4393da0a1fcbb773d9f56ac7523191

Tx prefix hash: 0c85444af86f13cc63718e52d651976b0132e1982d740ea032aed4608f8a018f
Tx public key: 1a7b7363c98857f3f222177ea0cacb1f58a8b095248c1a3db67a012a108c8416
Timestamp: 1583855843 Timestamp [UCT]: 2020-03-10 15:57:23 Age [y:d:h:m:s]: 05:029:01:28:22
Block: 79915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176490 RingCT/type: yes/0
Extra: 011a7b7363c98857f3f222177ea0cacb1f58a8b095248c1a3db67a012a108c8416021100000003640ff48f000000000000000000

1 output(s) for total of 333.601999182000 dcy

stealth address amount amount idx
00: a4035c228f15de5ebc1694fd865e7ed6a8f23285a6e3b1ed637ba27c9276e276 333.601999182000 146217 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": 79925, "vin": [ { "gen": { "height": 79915 } } ], "vout": [ { "amount": 333601999182, "target": { "key": "a4035c228f15de5ebc1694fd865e7ed6a8f23285a6e3b1ed637ba27c9276e276" } } ], "extra": [ 1, 26, 123, 115, 99, 201, 136, 87, 243, 242, 34, 23, 126, 160, 202, 203, 31, 88, 168, 176, 149, 36, 140, 26, 61, 182, 122, 1, 42, 16, 140, 132, 22, 2, 17, 0, 0, 0, 3, 100, 15, 244, 143, 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