Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55770bcbf7eeb2e850451f84ac316d41f35419f60d807e3a16a55ff0c16eaf3e

Tx prefix hash: 384fbfd761f2fd1e65fcf2592c730b6d8bb27c0ca7d2334b4e60b9e4ca2e675d
Tx public key: c4f24244e2c3dd34e93c0dfdd111f5f1a87154954cc316ce48002b0d31c1809b
Timestamp: 1598187224 Timestamp [UCT]: 2020-08-23 12:53:44 Age [y:d:h:m:s]: 05:046:22:29:47
Block: 129116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1256290 RingCT/type: yes/0
Extra: 01c4f24244e2c3dd34e93c0dfdd111f5f1a87154954cc316ce48002b0d31c1809b021100000007d81c26c0000000000000000000

1 output(s) for total of 229.184801304000 dcy

stealth address amount amount idx
00: 2704bf873ca94cf17b06b173504f763d289e9574f63308ac21055270fa049f35 229.184801304000 216644 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": 129126, "vin": [ { "gen": { "height": 129116 } } ], "vout": [ { "amount": 229184801304, "target": { "key": "2704bf873ca94cf17b06b173504f763d289e9574f63308ac21055270fa049f35" } } ], "extra": [ 1, 196, 242, 66, 68, 226, 195, 221, 52, 233, 60, 13, 253, 209, 17, 245, 241, 168, 113, 84, 149, 76, 195, 22, 206, 72, 0, 43, 13, 49, 193, 128, 155, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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