Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c1752b14bbfc1bdd34fb2fea2c9c1a519929219a33b58e720b21919bffb56e5

Tx prefix hash: 33ddbb163feac7153934cee5dbbf3cc4f5482df28f172660497e362945868a5e
Tx public key: b634d0b7aff0311fc84c8e634fb3f085eb2f8fa30fca280e85a9eb6aa1d7daa3
Timestamp: 1762559257 Timestamp [UCT]: 2025-11-07 23:47:37 Age [y:d:h:m:s]: 00:059:00:40:23
Block: 1407271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42284 RingCT/type: yes/0
Extra: 01b634d0b7aff0311fc84c8e634fb3f085eb2f8fa30fca280e85a9eb6aa1d7daa302110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f42cad69a8cc72361a1f21b69fc4b6b472555c98a4c0f98d660df23d202dd28d 0.600000000000 1895690 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": 1407281, "vin": [ { "gen": { "height": 1407271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f42cad69a8cc72361a1f21b69fc4b6b472555c98a4c0f98d660df23d202dd28d" } } ], "extra": [ 1, 182, 52, 208, 183, 175, 240, 49, 31, 200, 76, 142, 99, 79, 179, 240, 133, 235, 47, 143, 163, 15, 202, 40, 14, 133, 169, 235, 106, 161, 215, 218, 163, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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