Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e847252e152a83bf4ff123244b2b04231c2ed0565454995f0bf07a1a2fed998

Tx prefix hash: 483a673544bf6b1ff3d0b40f0dacb4ad96159c74555413d61dd02b0658be3c01
Tx public key: 18563d46d94811ee4482627abc0d420636ffc562e58d4915e33e3f4aa66e5f23
Timestamp: 1580117239 Timestamp [UCT]: 2020-01-27 09:27:19 Age [y:d:h:m:s]: 05:127:03:39:22
Block: 53822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241827 RingCT/type: yes/0
Extra: 0118563d46d94811ee4482627abc0d420636ffc562e58d4915e33e3f4aa66e5f23021100000003391a8d0e000000000000000000

1 output(s) for total of 407.067283321000 dcy

stealth address amount amount idx
00: b390bc6cc0c023f191670ef4da6e2c2af2dea68c048aabb7b1178f9fb0f78700 407.067283321000 99751 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": 53832, "vin": [ { "gen": { "height": 53822 } } ], "vout": [ { "amount": 407067283321, "target": { "key": "b390bc6cc0c023f191670ef4da6e2c2af2dea68c048aabb7b1178f9fb0f78700" } } ], "extra": [ 1, 24, 86, 61, 70, 217, 72, 17, 238, 68, 130, 98, 122, 188, 13, 66, 6, 54, 255, 197, 98, 229, 141, 73, 21, 227, 62, 63, 74, 166, 110, 95, 35, 2, 17, 0, 0, 0, 3, 57, 26, 141, 14, 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