Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f3fc9ef6da9244cefa8e58489751079b75908fb14b6c9748c00a4dedfa3f5f9

Tx prefix hash: 7d4cd6a21772bbd395e6f186da6d58173b1e2df49c2144e4e3c199494fbf64d2
Tx public key: fd920bd3a94c455964e5fc4e98b95640fb917859917de294cf26ebc7db0f755f
Timestamp: 1722385507 Timestamp [UCT]: 2024-07-31 00:25:07 Age [y:d:h:m:s]: 01:070:07:31:36
Block: 1077338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308687 RingCT/type: yes/0
Extra: 01fd920bd3a94c455964e5fc4e98b95640fb917859917de294cf26ebc7db0f755f02110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 251e2a21dbbf70aed7b0ad05f8f8b431fa41565a0288ecd25b23c67b698c1299 0.600000000000 1549885 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": 1077348, "vin": [ { "gen": { "height": 1077338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "251e2a21dbbf70aed7b0ad05f8f8b431fa41565a0288ecd25b23c67b698c1299" } } ], "extra": [ 1, 253, 146, 11, 211, 169, 76, 69, 89, 100, 229, 252, 78, 152, 185, 86, 64, 251, 145, 120, 89, 145, 125, 226, 148, 207, 38, 235, 199, 219, 15, 117, 95, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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