Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56142117757cede99a21a5dedc63a87ef29c31d4b26a2db8d9c73c35c4978553

Tx prefix hash: 4e730f387e9c79ad966350585f94b56a3a0429716aa60be2695de47e5961d852
Tx public key: 43cbbdfe4de4b93e91d96b4ad62408eb65eda6e7389439563fbb0c9abf8a2e3a
Timestamp: 1587780987 Timestamp [UCT]: 2020-04-25 02:16:27 Age [y:d:h:m:s]: 04:314:04:13:25
Block: 95524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136241 RingCT/type: yes/0
Extra: 0143cbbdfe4de4b93e91d96b4ad62408eb65eda6e7389439563fbb0c9abf8a2e3a021100000169a86a1a65000000000000000000

1 output(s) for total of 296.135246938000 dcy

stealth address amount amount idx
00: e5ebd44ead1d3dbf7db293bde29d26aa3dad08cb0e4680e3d1b7f4b4e84039ae 296.135246938000 169751 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": 95534, "vin": [ { "gen": { "height": 95524 } } ], "vout": [ { "amount": 296135246938, "target": { "key": "e5ebd44ead1d3dbf7db293bde29d26aa3dad08cb0e4680e3d1b7f4b4e84039ae" } } ], "extra": [ 1, 67, 203, 189, 254, 77, 228, 185, 62, 145, 217, 107, 74, 214, 36, 8, 235, 101, 237, 166, 231, 56, 148, 57, 86, 63, 187, 12, 154, 191, 138, 46, 58, 2, 17, 0, 0, 1, 105, 168, 106, 26, 101, 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