Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38422a33cf23981a0e049b2a4a656a2e9458708249f98fcafd51da74916d0eb0

Tx prefix hash: a4458f2191d20c2d22fe76a4a515d4f78f89f9a077f34f8a1afd454eb37a53f9
Tx public key: 6af19c891f9910e23c1c011886518eaa562f15c1fae9f5d708dc1f13124de8d7
Timestamp: 1760867256 Timestamp [UCT]: 2025-10-19 09:47:36 Age [y:d:h:m:s]: 00:101:22:04:38
Block: 1393266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72780 RingCT/type: yes/0
Extra: 016af19c891f9910e23c1c011886518eaa562f15c1fae9f5d708dc1f13124de8d7021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c4fc06eadce34c8b5b122fe67d96c3ebd8dfb0d641d73be39165d16e95d19e1 0.600000000000 1881529 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": 1393276, "vin": [ { "gen": { "height": 1393266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c4fc06eadce34c8b5b122fe67d96c3ebd8dfb0d641d73be39165d16e95d19e1" } } ], "extra": [ 1, 106, 241, 156, 137, 31, 153, 16, 226, 60, 28, 1, 24, 134, 81, 142, 170, 86, 47, 21, 193, 250, 233, 245, 215, 8, 220, 31, 19, 18, 77, 232, 215, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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