Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afb8e1670e6e0320b1f8fd39d93a38ba14fda1f6cca74e77bd549da9500118da

Tx prefix hash: fdd8c3e28132dd2bd8e0c7347d57981314e7e60a19614f60003211b6e709732a
Tx public key: 3a40306257d67d2df2ff2a841ffd543b4dda905971cc9e3356f96e5385f5cdf4
Timestamp: 1736486349 Timestamp [UCT]: 2025-01-10 05:19:09 Age [y:d:h:m:s]: 00:300:23:44:49
Block: 1194099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212611 RingCT/type: yes/0
Extra: 013a40306257d67d2df2ff2a841ffd543b4dda905971cc9e3356f96e5385f5cdf40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c35ecfc68dd7f2153f249a8e860db7dc1f0ef42a7ed8bf62f52297a66993a485 0.600000000000 1680666 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": 1194109, "vin": [ { "gen": { "height": 1194099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c35ecfc68dd7f2153f249a8e860db7dc1f0ef42a7ed8bf62f52297a66993a485" } } ], "extra": [ 1, 58, 64, 48, 98, 87, 214, 125, 45, 242, 255, 42, 132, 31, 253, 84, 59, 77, 218, 144, 89, 113, 204, 158, 51, 86, 249, 110, 83, 133, 245, 205, 244, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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