Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ad7d1dfa545bf73c3872208f57693e35a670d3574ad045282b596cd5ce0f02f

Tx prefix hash: 96eea01df3dc499f0b591bc3ca4d0088c242a954e630fa779caf1c6d35a5c88b
Tx public key: 51afa90ebc15c197699da6270624e34a8da07824f707918153ce29ecaf9b8ee5
Timestamp: 1633467632 Timestamp [UCT]: 2021-10-05 21:00:32 Age [y:d:h:m:s]: 03:224:10:28:54
Block: 347390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 937348 RingCT/type: yes/0
Extra: 0151afa90ebc15c197699da6270624e34a8da07824f707918153ce29ecaf9b8ee50211000000295410958b000000000000000000

1 output(s) for total of 43.346411376000 dcy

stealth address amount amount idx
00: 23fc10ec8c3171f6d504c5afe4cb7e1d109b281db9cfc97dba2a8e0c9555f113 43.346411376000 711878 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": 347400, "vin": [ { "gen": { "height": 347390 } } ], "vout": [ { "amount": 43346411376, "target": { "key": "23fc10ec8c3171f6d504c5afe4cb7e1d109b281db9cfc97dba2a8e0c9555f113" } } ], "extra": [ 1, 81, 175, 169, 14, 188, 21, 193, 151, 105, 157, 166, 39, 6, 36, 227, 74, 141, 160, 120, 36, 247, 7, 145, 129, 83, 206, 41, 236, 175, 155, 142, 229, 2, 17, 0, 0, 0, 41, 84, 16, 149, 139, 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