Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5fdc8f6800e73c0e3c4721a2d7a914ea40f4e85947a97b1a7eeeeea7fd77d49

Tx prefix hash: 545f80f7c7cdd3f3bdb0d684a789fb9c5aa4d70211645302118b4ab4bdc5595d
Tx public key: 40863089b7e8545a37778d624346f77fdd86e8a6a7720cb42bfcec237530f682
Timestamp: 1727098783 Timestamp [UCT]: 2024-09-23 13:39:43 Age [y:d:h:m:s]: 00:190:06:31:30
Block: 1116410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135787 RingCT/type: yes/0
Extra: 0140863089b7e8545a37778d624346f77fdd86e8a6a7720cb42bfcec237530f68202110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de660e9ff7080a24801a8fa39942202ea65c1270708ec4dc020126f99466c1a0 0.600000000000 1596881 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": 1116420, "vin": [ { "gen": { "height": 1116410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de660e9ff7080a24801a8fa39942202ea65c1270708ec4dc020126f99466c1a0" } } ], "extra": [ 1, 64, 134, 48, 137, 183, 232, 84, 90, 55, 119, 141, 98, 67, 70, 247, 127, 221, 134, 232, 166, 167, 114, 12, 180, 43, 252, 236, 35, 117, 48, 246, 130, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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