Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83b805441ae2fae1a9c1037ddfd1831e25c24927d9198743c4669d532729d9e6

Tx prefix hash: c321807059d0c541544aca6901b1429b33215d18ab0d049e2a8f19c9a4563c83
Tx public key: 027f7ceeaed40b00b7ca33e5f62cda5b27cba10bcb0d8639dc30042c37228ab7
Timestamp: 1717447005 Timestamp [UCT]: 2024-06-03 20:36:45 Age [y:d:h:m:s]: 01:157:10:31:31
Block: 1036398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371087 RingCT/type: yes/0
Extra: 01027f7ceeaed40b00b7ca33e5f62cda5b27cba10bcb0d8639dc30042c37228ab702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f846342d46651df6c07fcbfa75ef2d688fdc6afc0b79a5071981e5450ac81e 0.600000000000 1504925 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": 1036408, "vin": [ { "gen": { "height": 1036398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f846342d46651df6c07fcbfa75ef2d688fdc6afc0b79a5071981e5450ac81e" } } ], "extra": [ 1, 2, 127, 124, 238, 174, 212, 11, 0, 183, 202, 51, 229, 246, 44, 218, 91, 39, 203, 161, 11, 203, 13, 134, 57, 220, 48, 4, 44, 55, 34, 138, 183, 2, 17, 0, 0, 0, 2, 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