Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ef79a3d0e500d7b41a975b2a85147bc41dbe2ca5fdbd3985e3fc89ce575298

Tx prefix hash: 4b96acd676cdad2e4e125b70e344eac5d979563ae9c26b8783287d0b5f0fea39
Tx public key: 1ec75344e80973d5a7a45d404986fc9f33656867962055d56cf913747d7b39a4
Timestamp: 1747095939 Timestamp [UCT]: 2025-05-13 00:25:39 Age [y:d:h:m:s]: 00:232:12:13:37
Block: 1281657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163947 RingCT/type: yes/0
Extra: 011ec75344e80973d5a7a45d404986fc9f33656867962055d56cf913747d7b39a40211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 193c4e9eb13ac0b8f8053a53a2852eb462f760e9c1d99ae1eafcedd1a6a390f3 0.600000000000 1769058 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": 1281667, "vin": [ { "gen": { "height": 1281657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "193c4e9eb13ac0b8f8053a53a2852eb462f760e9c1d99ae1eafcedd1a6a390f3" } } ], "extra": [ 1, 30, 199, 83, 68, 232, 9, 115, 213, 167, 164, 93, 64, 73, 134, 252, 159, 51, 101, 104, 103, 150, 32, 85, 213, 108, 249, 19, 116, 125, 123, 57, 164, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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