Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e2d6b91696af1dc406f632ca54507b2d57668d5ef8bdb4e8ed3f5c02fe05355

Tx prefix hash: 6a0cfd773b00a54d75e022a8a8df303649b8cddcbf7ebcd86f20bd562d375997
Tx public key: 41dc95bcda5b4d9f2b75b9ea262bc16d98d986004d8fdfd70fd2dc77b4f344e0
Timestamp: 1742146692 Timestamp [UCT]: 2025-03-16 17:38:12 Age [y:d:h:m:s]: 00:240:15:34:02
Block: 1240709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169700 RingCT/type: yes/0
Extra: 0141dc95bcda5b4d9f2b75b9ea262bc16d98d986004d8fdfd70fd2dc77b4f344e00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49894f36de11fff4fb9d521014d63a3b95259ef21332ed8c1f7504e0bfbc50e0 0.600000000000 1727682 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": 1240719, "vin": [ { "gen": { "height": 1240709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49894f36de11fff4fb9d521014d63a3b95259ef21332ed8c1f7504e0bfbc50e0" } } ], "extra": [ 1, 65, 220, 149, 188, 218, 91, 77, 159, 43, 117, 185, 234, 38, 43, 193, 109, 152, 217, 134, 0, 77, 143, 223, 215, 15, 210, 220, 119, 180, 243, 68, 224, 2, 17, 0, 0, 0, 2, 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