Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49015dbf1da2f486f5d41307b628a044c5c0a4ff9ef34dc2506d351277ed6e9f

Tx prefix hash: 1ef875f6fb58134253b6dc9dbb5994124f15cc67cad9b6077977c0974cb8aab8
Tx public key: a8a5e37501bbd0d36da9d948e798f67fc9d9130ed4f19115bb9e333ac7334304
Timestamp: 1617570388 Timestamp [UCT]: 2021-04-04 21:06:28 Age [y:d:h:m:s]: 03:336:07:12:52
Block: 233290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 999853 RingCT/type: yes/0
Extra: 01a8a5e37501bbd0d36da9d948e798f67fc9d9130ed4f19115bb9e333ac7334304021100000071ece3035d000000000000000000

1 output(s) for total of 103.524544924000 dcy

stealth address amount amount idx
00: d38591839f713cd0492e83f48f0fa189c7a02eb65f45a9b6847e40b63c228415 103.524544924000 484512 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": 233300, "vin": [ { "gen": { "height": 233290 } } ], "vout": [ { "amount": 103524544924, "target": { "key": "d38591839f713cd0492e83f48f0fa189c7a02eb65f45a9b6847e40b63c228415" } } ], "extra": [ 1, 168, 165, 227, 117, 1, 187, 208, 211, 109, 169, 217, 72, 231, 152, 246, 127, 201, 217, 19, 14, 212, 241, 145, 21, 187, 158, 51, 58, 199, 51, 67, 4, 2, 17, 0, 0, 0, 113, 236, 227, 3, 93, 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