Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24b1235f1d02c55afb8c7f80be8e944e1a60acf3788fc89528f6e639becd78b

Tx prefix hash: c91e5bbe6de74768b49aef9caf6e8c915f9e1ec5b11e899d769c722549a6f27b
Tx public key: 6fac9871efa95ef7f65904b43be7760b119511a43e4dea59d9837311604af22a
Timestamp: 1629611558 Timestamp [UCT]: 2021-08-22 05:52:38 Age [y:d:h:m:s]: 04:118:06:41:42
Block: 318639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116929 RingCT/type: yes/0
Extra: 016fac9871efa95ef7f65904b43be7760b119511a43e4dea59d9837311604af22a021100000028b75ebe6a000000000000000000

1 output(s) for total of 53.978988953000 dcy

stealth address amount amount idx
00: 03954363af1bc2b52d3c17fdcf3d3c4f725a646561632d6b2c39ba2c2a396b97 53.978988953000 662240 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": 318649, "vin": [ { "gen": { "height": 318639 } } ], "vout": [ { "amount": 53978988953, "target": { "key": "03954363af1bc2b52d3c17fdcf3d3c4f725a646561632d6b2c39ba2c2a396b97" } } ], "extra": [ 1, 111, 172, 152, 113, 239, 169, 94, 247, 246, 89, 4, 180, 59, 231, 118, 11, 17, 149, 17, 164, 62, 77, 234, 89, 217, 131, 115, 17, 96, 74, 242, 42, 2, 17, 0, 0, 0, 40, 183, 94, 190, 106, 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