Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e59186a0b8003d673675927aaea39e31f53cb19fb83e790ce5875578c833690b

Tx prefix hash: d4b2130f62115f5106eed64e9474c6c4f6a83cb6eb45c9aa4286b9facd6f8f0f
Tx public key: 584c189a902a52183f0259857dd068aff336b6f7c2e8a03ca819335818887f50
Timestamp: 1713248922 Timestamp [UCT]: 2024-04-16 06:28:42 Age [y:d:h:m:s]: 01:042:22:28:02
Block: 1001564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291694 RingCT/type: yes/0
Extra: 01584c189a902a52183f0259857dd068aff336b6f7c2e8a03ca819335818887f5002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab14cc0124d499a7ba793ff3aed94e2d28da4501dc7fd6bb35578e0d37ebfe3 0.600000000000 1462070 of 15

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": 1001574, "vin": [ { "gen": { "height": 1001564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab14cc0124d499a7ba793ff3aed94e2d28da4501dc7fd6bb35578e0d37ebfe3" } } ], "extra": [ 1, 88, 76, 24, 154, 144, 42, 82, 24, 63, 2, 89, 133, 125, 208, 104, 175, 243, 54, 182, 247, 194, 232, 160, 60, 168, 25, 51, 88, 24, 136, 127, 80, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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